We are quickly transitioning over from Organization Insights which came as a managed solution inside D365 to CDS For Apps Analytics on the PowerPlatform Admin Center. And now, the same is revamped as Capacity in PowerPlatform Admin Center. So, if you go to Storage in CDS For Apps analytics, you’ll see this – Capacity You can access Capacity section directory from this URL – https://admin.powerplatform.microsoft.com/analytics/capacity Or from the left hand menu as below – Now, as opposed to previously summarized % of the total capacity available, Microsoft is providing new entitlements for different types of storage consumption – Zoomed below As mentioned above, the bifurcation is as follows – DATABASE: All other entities apart from the ones mentioned below. FILE: Attachment, AnnotationBase tables LOG: AuditBase, PluginTraceLogBase tables Environment View A Per Environment View looks like below and you can click on the Graph icon to go into the details At this point, information for the Graphical details are yet to be available. I’ll update post this is available for me too. Availability New Capacity model differs and will be available once the current term ends. More information from the links in the More Information section below More Information You can refer more on Capacity here – https://docs.microsoft.com/en-us/power-platform/admin/capacity-storage Hope this quick summary helps!

Most times when you want to use AddCustomView() method to a Dynamics 365 control, you need to pass layoutXml to the method that will show the view you define. There’s an easier trick than writing this up. Select your View Assuming, you have an Advanced Find view open in the window which you want as a layoutXml of, on the same, press F12 to open Dev Tools. Select the selector. And on the Advanced Find window, select Body section Click on it, and the par will be selected in the Console of the Dev Tools. Once this is available, search for layoutXml and cycle through the results to go to the last result. select the “value” part. That is your layoutXml. Hope this helps.

Dynamics 365 for Customer Service is the right ERP software to use if you desire to see the customer service improvement in your company. When businesses provide excellent customer support, clients not only have the best experiences, but they also stay loyal to a business. Of course, there are so many ERP solutions out there in the market. Dynamics 365 solutions are, however, the best in the world as many companies tried and tested this product and love the way it helps them to become a lot more organized. Since Microsoft owns this product, they do a lot of research to enhance this particular product. One problem people do not know how to fix is the infinite loop issue. Here are some fantastic tips to help you to surpass the problem. While using fetch xml to retrieve records more than 5000 records and if you have multiple entities involve in it. There are chances that you will get into an infinite loop even if you have less than 5000 records. Description: We have noticed that after 9.0 if you are using the old method to retrieve more that 5000 records using the fetch xml in the script it is possible that you will get the into infilter loop. This happens due to the internal multiplication of table which gives fist and last records id same in fetch XML. You need to make sure that include the header as shown in the below screen Need to make sure that you have below check condition before calling the fetch next record collection if (data[“@Microsoft.Dynamics.CRM.fetchxmlpagingcookie”] != null && data[“@Microsoft.Dynamics.CRM.morerecords”] != null && data[“@Microsoft.Dynamics.CRM.morerecords”]==true) { It has more than 1 record true only than call the next request Conclusion Hope this helps you to solve your infinite loop issue.

Dynamics 365 for customer service assists businesses to provide efficient and excellent customer service to improve customer service in a team. When it comes to business, every interaction that you get from your customer does matter a lot. Maximizing brand loyalty is only possible when customers get their problems or issues resolved quickly. Companies need to invest in Dynamics 365 solutions if they desire to provide the best customer service to their existing and prospective customers. It has some of the best features that can enhance your business operations. And the best part, it is quite economical than all other solutions that you now find in the market. There are so many resources that are available to make things easy for those who install and use it. We had a requirement where need to open the newly created record. Here we were using an action to create the record. Description: We had a requirement on button click contact will be created and once the record is created we need to open that record as well. Opening of the record is dependent on the user if he wants open or not. we have created a custom button and call the action which perform the operation of creation of the record. this record was created inside the action Below action was created and called on the button. 2. Output parameter was defined for the contact record that has been created inside the action 3. Once the contact record is created we set newly created contact guide as an output parameter. 4. Once that is done we got the contact id as a parameter and open it using the open form request in CRM Conclusion Hope this helps while setting output parameter value using the action.

If you want to set the alternate key to detecting duplicate record based on lookup it was not earlier. If you want to have duplicated detection based on you would not be able to that you have to write a plugin to get that result. Description: You can now achieve a duplicate detection rule by defining the lookup as an alternate key. You can create an alternate key by following the below steps To define the alternate keys, go to Go to Settings> Customizations Choose Customize the System–>Components ->Entities –> Entity–>Keys. Choose New. 3. On the form, fill in the required fields (Display Name and Name) and then choose and add the fields to the key. Save the key. In the example shown here, we used the ParentId field in the alternate key definition. Conclusion Hope this helps while defining the alternate key with lookup/entity reference

Introduction Sometime there is requirement where we need to set a null value based on certain condition. We usually use script to set the null value this can be achieved using the workflow. Description: To set the null value of you need to create a new workflow. Follow the below steps. Go to setting —> Process 2. Create new work flow 3. Set clear value for field which is you want to set the null value as shown as below. 4. Set the value and save the work flow. Conclusion Hope this helps while setting null value using the flow.

Introduction While using fetch XML to retrieve records more than 5000 records and if you have multiple entities involve in it. There are chances that you will get into an infinite loop even if you have less than 5000 records. Description: We have noticed that after 9.0 if you are using the old method to retrieve more that 5000 records using the fetch xml in the script it is possible that you will get the into infilter loop. This happens due to the internal multiplication of table which gives fist and last records id same in fetch xml You need to make sure that include the header as shown in the below screen Need to make sure that you have below check condition before calling the fetch next record collection if (data[“@Microsoft.Dynamics.CRM.fetchxmlpagingcookie”] != null && data[“@Microsoft.Dynamics.CRM.morerecords”] != null && data[“@Microsoft.Dynamics.CRM.morerecords”]==true) { It has more than 1 record true only than call the next request. Conclusion Hope this helps you to solve your infinite loop issue.

Introduction While fetching images using fetch XML there is a possibility that you will not able to get the complete image. You will also notice that these issues generally happens when you are using multiple internal entities. Description: We were working on a project where we displaying the records notes using the multiple entities, we noticed that it is not showing the complete images, but it is truncated or incomplete. Let’s see the actual query and the output Scenario 1: In the below query we are getting the incomplete images as a base 64 string. Result Scenario 2 In the below fetch xml we are getting complete image If you will closely look into the query distinct parameter for the first was true whereas in the second case it was false. Conclusion Hope this helps you to retrieve the complete image and not the truncated one

Introduction While working with workflow, we can map the same data type field while creating or updating a record. But there was an issue with optionset mapping. Description: I have used workflow quite a lot time but recently I was mapping an option set with another option set which has the same value, but it was not showing the value. I found that due to local option set not allowed to map. As you can see in the below screen it is not showing the field to map. To overcome with this, we need to perform the below three steps 1.) Create a global option set 2.) Create local option set using the global option set on source record 3.) Create local option set using the global option set on target record Once above field is created you will able to see the mapping field Note: 1.) Since we are creating another field, make sure that you have kept the history value of old record. 2.) Do not delete the field while creating new field mapping Conclusion: Hope this helps you to map optionset using workflow.

Introduction While working with dynamics 365 sales we can send email within system using workflow. We can configure the same for other user to send email using Workflow to send mail. Description: But it is possible that other users may start receiving below show error. The above error clearly shows that it is missing “Send as privilege”. This error occurs while sending email from other user email id is other than the user who is sending the email. Here owner of the workflow needs to give access to send the email to other user on his behalf. You can follow the below steps to allow the “send as privilege” You need to set the Workflow Owner user settings via the Workflow Owner User Options; Person Options > Email > Allow other Microsoft Dynamics CRM users to send email on your behalf. You will have to log into workflow owners crm account to set this, and will allow the workflows to send emails Also, the user who is sending the email must have the below security privilege as well. Conclusion: Hope this helps while send email from another users account.